Skip to content

feat(backend): Builder search history #11457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from
Draft

feat(backend): Builder search history #11457

wants to merge 1 commit into from

Conversation

@kcze
Copy link
Contributor

@kcze kcze commented Nov 26, 2025

Changes 🏗️

Checklist 📋

For code changes:

  • I have clearly listed my changes in the PR description
  • I have made a test plan
  • I have tested my changes according to the test plan:
    • ...

@github-project-automation github-project-automation bot moved this to 🆕 Needs initial review in AutoGPT development kanban Nov 26, 2025
@netlify
Copy link

netlify bot commented Nov 26, 2025 •
edited
Loading

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name Link
🔨 Latest commit b3c3f9c
🔍 Latest deploy log https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/6927b71a7f47740008116291

@coderabbitai
Copy link

coderabbitai bot commented Nov 26, 2025 •
edited
Loading

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch kpczerwinski/secrt-1731-builder-search-history

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@netlify
Copy link

netlify bot commented Nov 26, 2025 •
edited
Loading

✅ Deploy Preview for auto-gpt-docs canceled.

Name Link
🔨 Latest commit b3c3f9c
🔍 Latest deploy log https://app.netlify.com/projects/auto-gpt-docs/deploys/6927b71af63b7c0008e483a9

@deepsource-io
Copy link

deepsource-io bot commented Nov 26, 2025 •
edited
Loading

Here's the code health analysis summary for commits e983d5c..b3c3f9c. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗
DeepSource Python LogoPython✅ SuccessView Check ↗
💡 If you’re a repository administrator, you can configure the quality gates from the settings.

@AutoGPT-Agent
Copy link

AutoGPT-Agent commented Nov 26, 2025

Thank you for your PR! Before we can proceed with merging, there are a few issues that need to be addressed:

  1. Your PR description is missing information about the changes you've made. Please fill in the 'Changes' section to describe what your builder search history implementation does.

  2. None of the items in the checklist have been checked off. Please complete the checklist by checking the boxes for items you've completed. At minimum:

    • Confirm you've clearly listed your changes
    • Indicate you've made a test plan
    • Note that you've tested your changes according to that plan (and include the test plan)

  3. The diff appears to be empty in this review - if you've made code changes, please ensure they're properly committed and showing in the PR.

Once you've updated these items, we can proceed with a more thorough review of your implementation. The PR title looks good with the proper conventional commit format.

@github-actions github-actions bot added the platform/frontend AutoGPT Platform - Front end label Nov 26, 2025
@AutoGPT-Agent
Copy link

AutoGPT-Agent commented Nov 26, 2025

Thank you for your contribution! There are a few items that need to be addressed before this PR can be merged:

  1. The PR title mentions "feat(backend): Builder search history" but the changes are to a frontend wallet component. Please update your PR title to accurately reflect your changes (perhaps something like "fix(frontend): Wallet component condition check").

  2. The PR description is empty. Please explain:

    • What issue this PR is solving
    • What specific changes you've made

  3. The checklist needs to be completed - either check off the items or remove the checklist if the changes are not material (this appears to be a small bugfix).

Once these issues are addressed, we can proceed with the review. The code change itself looks straightforward, but we need proper documentation to understand its purpose.

@kcze kcze force-pushed the kpczerwinski/secrt-1731-builder-search-history branch from 987baa9 to b3c3f9c Compare November 27, 2025 02:27
@AutoGPT-Agent
Copy link

AutoGPT-Agent commented Nov 27, 2025

Thank you for your PR contribution. Before this can be merged, please update the following:

  1. Ensure your PR title and labels are consistent. Your title mentions backend changes, but the PR is labeled as frontend.

  2. Complete the PR description to explain the purpose of these changes and what they accomplish.

  3. Fill out the checklist completely.

  4. Ensure your PR includes the actual code changes (the diff is currently empty).

Once you've addressed these points, please request another review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

platform/frontend AutoGPT Platform - Front end size/s size/xs

Projects

AutoGPT development kanban
Status: 🆕 Needs initial review
Frontend
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@kcze @AutoGPT-Agent